Memory card and non-volatile memory controller thereof

ABSTRACT

A memory card and a non-volatile memory controller thereof are provided. The non-volatile memory controller includes a firmware download port group, a memory interface unit, a processing unit, and a host interface unit. The firmware download port group is used for coupled to a firmware update fixture. The memory interface unit includes at least one tri-state buffer component, and the memory interface unit is coupled to a non-volatile memory and the firmware download port group through the tri-state buffer component, wherein the tri-state buffer component determines whether to operate in a high-impedance mode or a normal mode according to a mode single. The processing unit accesses the non-volatile memory through the memory interface unit. When the tri-state buffer component operates in the high-impedance mode according to the mode single, the firmware update fixture writes a new firmware into the non-volatile memory through the firmware download port group.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the priority benefit of Taiwan applicationserial no. 971131802, filed on Aug. 20, 2008. The entirety of theabove-mentioned patent application is hereby incorporated by referenceherein and made a part of this specification.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to a memory controller, and moreparticularly, to a non-volatile memory controller which can update afirmware directly on a printed circuit board and a memory card using thesame.

2. Description of Related Art

Along with the rapid advancement of information technology, storagemedia developed based on semiconductor techniques have become themainstream products and which are generally referred to as portablememories, flash memory cards, or memory cards. Compared to theconventional floppy disk and compact disk, portable memory is far moreadvantageous in its functional characteristics, such as portability,power consumption, data storage, data transmission rate, reread orrewrite, and vibration and damp proof. Due to all these advantages ofportable memory, every international electronic product manufacturer haspromoted its own portable memory, such as Smart card, PC card (PCMCIAATA Flash Card), CF card (CompactFlash Card), SM card (Smart MediaCard), MMC card (MultiMedia Card), MS card (Memory Stick Card), and SDcard (Secure Digital Card), etc, and these portable memories are broadlyapplied to various digital products. Generally, after a memory card ismanufactured, a firmware has to be written into the memory card by usinga special fixture called MP-tooling (usually provided by themanufacturer of the memory card).

FIG. 1 is a functional block diagram illustrating how a firmware iswritten into a conventional multi-chip package (MCP) memory card.Referring to FIG. 1, the MCP integrated circuit (IC) 110 includes anon-volatile memory controller 120 and a plurality of non-volatilememories 160 and 170. The non-volatile memory controller 120 furtherincludes an interface circuit 121, a processing unit 122, and a memorycontrol unit 123. The MCP IC 110 may be a memory chip package conformingto the specification of Smart card, PC card, or SD card, etc.

Herein it is assumed that the non-volatile memory controller 120 is a SDmemory card controller, and the non-volatile memories 160 and 170 areflash memory chips. If an external device, for example, a host 140, ofthe MCP IC 110 is about to access the non-volatile memory 160 or 170,the host 140 has to send a signal to the interface circuit 121 accordingto the specification of SD memory card. After a fixture 190 receives anew firmware, the fixture 190 sends the new firmware to the processingunit 122 through the interface circuit 121, and the processing unit 122then writes the new firmware into the non-volatile memory 160 throughthe memory control unit 123.

In another conventional firmware updating technique, when the memorycard becomes invalid or has compatibility problem and accordingly thefirmware in the MCP IC 110 is to be updated, the MCP IC 110 soldered ona printed circuit board (PCB) is de-soldered (i.e., removed from thePCB) and then loaded into a specific firmware update fixture 190 to bewritten with the new firmware. Accordingly, this conventional techniqueis very inconvenient and costly.

SUMMARY OF THE INVENTION

Accordingly, the present invention is directed to a non-volatile memorycontroller which can update a firmware directly on a printed circuitboard, such that firmware update is made more convenient.

The present invention is also directed to a memory card which can updatea firmware directly on a printed circuit board.

The present invention provides a non-volatile memory controllerincluding a firmware download port group, a memory interface unit, aprocessing unit, and a host interface unit. The firmware download portgroup is used for coupled to a firmware update fixture. The memoryinterface unit includes at least one tri-state buffer component, and thememory interface unit is coupled to a non-volatile memory and thefirmware download port group through the ti-state buffer component,wherein the tri-state buffer component determines whether to operate ina high-impedance mode or a normal mode according to a mode signal. Theprocessing unit is coupled to the memory interface unit, and theprocessing unit accesses the non-volatile memory through the memoryinterface unit. The host interface unit is coupled to the processingunit. The processing unit provides a processing interface through thehost interface unit to allow a host to access the non-volatile memory.When the tri-state buffer component operates in the high-impedance modeaccording to the mode signal, the firmware update fixture writes a newfirmware into the non-volatile memory through the firmware download portgroup.

The present invention also provides a memory card including anon-volatile memory and a non-volatile memory controller. Thenon-volatile memory controller includes a firmware download port group,a memory interface unit, a processing unit, and a host interface unit.The firmware download port group is coupled to a firmware updatefixture. The memory interface unit includes at least one tri-statebuffer component, and the memory interface unit is coupled to thenon-volatile memory and the firmware download port group through thetri-state buffer component, wherein the tri-state buffer componentdetermines whether to operate in a high-impedance mode or a normal modeaccording to a mode signal. The processing unit is coupled to the memoryinterface unit, and the processing unit accesses the non-volatile memorythrough the memory interface unit. The host interface unit is coupled tothe processing unit. The processing unit provides a processing interfacethrough the host interface unit to allow a host to access thenon-volatile memory. When the tri-state buffer component operates in thehigh-impedance mode according to the mode signal, the firmware updatefixture writes a new firmware into the non-volatile memory through thefirmware download port group.

According to an embodiment of the present invention, the tri-statebuffer component is a tri-state buffer.

According to an embodiment of the present invention, the tri-statebuffer component includes a buffer and a switch, wherein the switch iscoupled between the buffer and the non-volatile memory, and the switchis in an “off” state in the high-impedance mode while in an “on” statein the normal mode.

According to an embodiment of the present invention, the non-volatilememory controller and the non-volatile memory are both packaged in amulti-chip package (MCP).

According to an embodiment of the present invention, a lower side of theMCP is soldered on a printed circuit board (PCB), and the firmwaredownload port group is disposed on an upper side of the MCP.

According to an embodiment of the present invention, a lower side of theMCP is soldered on a PCB, and the firmware download port group isdisposed at an edge of the lower side of the MCP.

According to an embodiment of the present invention, a packaged lowerside of the non-volatile memory controller is soldered on a PCB, and thefirmware download port group is disposed on a packaged upper side of thenon-volatile memory controller.

According to an embodiment of the present invention, a packaged lowerside of the non-volatile memory controller is soldered on a PCB, and thefirmware download port group is disposed at an edge of the packagedlower side of the non-volatile memory controller.

According to an embodiment of the present invention, the non-volatilememory controller further comprises a first memory port group coupledbetween a control unit and the non-volatile memory.

In the present invention, to update the firmware in a non-volatilememory, a mode signal is input into a memory interface unit to allow atri-state buffer in the memory interface unit to operate in ahigh-impedance mode, so that a firmware update fixture can directlywrite a new firmware into the non-volatile memory on a printed circuitboard. Thereby, firmware update is made more convenient.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a furtherunderstanding of the invention, and are incorporated in and constitute apart of this specification. The drawings illustrate embodiments of theinvention and, together with the description, serve to explain theprinciples of the invention.

FIG. 1 is a functional block diagram illustrating how a firmware iswritten into a conventional multi-chip package (MCP) memory card.

FIG. 2 is a functional block diagram of a memory card according to anembodiment of the present invention.

FIG. 3 is a functional block diagram of a non-volatile memory controlleraccording to an embodiment of the present invention.

FIG. 4 is a functional block diagram of a non-volatile memory controlleraccording to another embodiment of the present invention.

FIG. 5 is a functional block diagram of a non-volatile memory controlleraccording to yet another embodiment of the present invention.

FIG. 6 is a functional block diagram of a non-volatile memory controlleraccording to still another embodiment of the present invention.

FIG. 7 is a diagram illustrating the disposition of pins of a MCPaccording to an embodiment of the present invention.

FIG. 8 is a diagram illustrating the connection between a MCP and afixture according to an embodiment of the present invention.

FIG. 9 is an exploded view illustrating the connection between a MCP anda fixture according to another embodiment of the present invention.

FIG. 10 is an exploded view illustrating the connection between a MCPand a fixture according to yet another embodiment of the presentinvention.

FIG. 11 is a flowchart of a firmware updating process according to anembodiment of the present invention.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the present preferredembodiments of the invention, examples of which are illustrated in theaccompanying drawings. Wherever possible, the same reference numbers areused in the drawings and the description to refer to the same or likeparts.

First Embodiment

FIG. 2 is a functional block diagram of a memory card according to thefirst embodiment of the present invention. Referring to FIG. 2, thenon-volatile memory controller 200 provides a processing interfacebetween a host 140 and a non-volatile memory 160 to allow the host 140to access the non-volatile memory 160. In the present embodiment, thenon-volatile memory controller 200 and the non-volatile memory 160 areboth packaged in a multi-chip package (MCP) 290. The present embodimentcan be applied to a non-volatile memory controller of any type and anyspecification. For example, the non-volatile memory controller 200 maybea memory controller conforming to the specification of any memory cardin the market, such as a smart card, a PC card, a CF card, a SM card, aMMC card, a MS card, or a SD card. Besides, in the present embodiment,the non-volatile memory 160 may be any programmable read-only memory(ROM), such as a flash memory or an electrically erasable programmableread-only memory (EEPROM).

The non-volatile memory controller 200 includes a host interface unit220, a processing unit 122, a memory interface unit 240, a firmwaredownload port group 280, and a memory port group 260. In the presentembodiment, the memory interface unit 240 includes a memory control unit242 and a tri-state buffer component 241. The memory control unit 242can be implemented in any pattern. For example, the memory control unit242 may be implemented with the same circuit as the memory control unit123 illustrated in FIG. 1. In addition, the tri-state buffer component241 in the present embodiment is a tri-state buffer. The firmwaredownload port group 280 and the memory port group 260 may be boundingpad groups of the non-volatile memory controller 200.

The firmware download port group 280 is coupled to a firmware updatefixture 230. The memory interface unit 240 is coupled to thenon-volatile memory 160 and the firmware download port group 280 throughthe tri-state buffer component 241. The processing unit 122 is coupledto the memory interface unit 240, and the host interface unit 220 iscoupled to the processing unit 122.

Through the control of a control terminal, the tri-state buffercomponent 241 can let its output terminal to operate in a normal mode(to output logic 0 or logic 1) or a high-impedance mode (the outputterminal being in a high-impedance state). For example, in the presentembodiment, the tri-state buffer 241 of the memory interface unit 240determines whether to operate in the high-impedance mode or the normalmode according to a mode signal 250. If the mode signal 250 receivedfrom the input terminal B of the tri-state buffer 241 is disabled (atlow level), then there will be no current at the output terminal C ofthe tri-state buffer 241, namely, the output terminal C is in ahigh-impedance state. Thus, regardless of whether the input terminal Aof the tri-state buffer 241 is at high level or low level, the outputterminal C thereof is always in an “open” state, and the tri-statebuffer 241 operates in the high-impedance mode. Contrarily, if the modesignal 250 received from the input terminal B of the tri-state buffer241 is enabled (at high level), the output terminal C of the tri-statebuffer 241 is equal to the input terminal A thereof, and the tri-statebuffer 241 operates in the normal mode.

The processing unit 122 accesses the non-volatile memory 160 through thememory interface unit 240. The host interface unit 220 is coupled to theprocessing unit 122. The processing unit 122 provides a processinginterface to the host 140 through the host interface unit 220 so thatthe host 140 can access the non-volatile memory 160 through theprocessing interface. When the processing unit 122 processes an accessrequest of the host 140, the memory control unit 242 performscorresponding operations to the non-volatile memory 160 according to theinstructions of the processing unit 122.

Normally, the mode signal 250 controls the tri-state buffer component241 to be in an enabled state (in the normal mode). Thus, when the host140 is about to access the non-volatile memory 160, the host 140 canaccess the non-volatile memory 160 through the non-volatile memorycontroller 200.

It should be noted that if a firmware stored in the non-volatile memory160 is to be updated, the mode signal 250 controls the tri-state buffercomponent 241 to be in an disabled state (in the high-impedance mode) sothat the output terminal C of the tri-state buffer (the tri-state buffercomponent 241) is in the “open” state. In this case, the firmware updatefixture 230 is connected to the firmware download port group 280. Thus,in this case, only the firmware update fixture 230 is connected to thenon-volatile memory 160 through the firmware download port group 280 andthe memory port group 260. Then the firmware update fixture 230 writes anew firmware into the non-volatile memory 160 through the firmwaredownload port group 280 and the memory port group 260 based on an accessprotocol compatible to the non-volatile memory 160. Since the circuitpath connected to the non-volatile memory 160 is always switched to the“open” state in the high-impedance mode, no other circuit will beaffected when the firmware update fixture 230 writes the new firmwareinto the non-volatile memory 160. As a result, the problem of buscontention is avoided. Thereby, the non-volatile memory controller 200in the present invention can update a firmware directly on a printedcircuit board. Accordingly, firmware update is made more convenient.

The mode signal 250 is an external signal of the non-volatile memorycontroller 200 and which can be set through any method. For example, themode signal 250 can be provided/set by the firmware update fixture 230.When the firmware update fixture 230 is connected to the non-volatilememory controller 200, the firmware update fixture 230 makes thetri-state buffer component 241 to operate in the high-impedance modethrough the control of the mode signal 250 and then writes the newfirmware into the non-volatile memory 160 through the firmware downloadport group 280 and the memory port group 260. In another embodiment ofthe present invention, the mode signal 250 may also be set by using ajumper element disposed on the printed circuit board (PCB).

In the embodiment described above, the non-volatile memory controller200 and the non-volatile memory 160 can be integrated into the same IC(or chip) or may also be implemented in different ICs (or chips). If thenon-volatile memory controller 200 and the non-volatile memory 160 arerespectively implemented in different ICs (or chips), they can befabricated through any packaging technique. For example, thenon-volatile memory controller 200 and the non-volatile memory 160 canbe packaged together into a MCP. Or, the non-volatile memory controller200 and the non-volatile memory 160 can be respectively packaged indifferent IC packages.

Second Embodiment

FIG. 3 is a functional block diagram of a non-volatile memory controller300 according to the second embodiment of the present invention. Thedifference between the first embodiment illustrated in FIG. 2 and thesecond embodiment illustrated in FIG. 3 is that in the secondembodiment, the function of the tri-state buffer component 330 in thememory interface unit 320 is accomplished by using different elements.Referring to FIG. 3, the tri-state buffer component 330 in the memoryinterface unit 320 includes a buffer 340 and a switch 360. The switch360 is coupled between the buffer 340 and the non-volatile memory 160.The switch 360 is in an “off” state in the high-impedance mode while inan “on” state in the normal mode. Besides the memory interface unit 320,the other functional blocks in FIG. 3 are similar to those in FIG. 2therefore will not be described herein.

The switch 360 can be turned on (i.e., in the normal mode) or turned off(i.e., in the high-impedance mode) through the control of the modesignal 250. For example, in the normal mode, the mode signal 250 turnson the switch 360. Accordingly, when the host 140 is about to access thenon-volatile memory 160, the host 140 can access the non-volatile memory160 through the non-volatile memory controller 300. In addition, if afirmware stored in the non-volatile memory 160 is to be updated, thetri-state buffer component 330 is allowed to operate in thehigh-impedance mode (i.e., the switch 360 is in the “off” state) bysetting the state of the mode signal 250. Then, the firmware updatefixture 230 is connected to the firmware download port group 280. Inthis case, only the firmware update fixture 230 is connected to thenon-volatile memory 160 through the firmware download port group 280 andthe memory port group 260. Thus, the firmware update fixture 230 canupdate the firmware in the non-volatile memory 160 through the firmwaredownload port group 280 and the memory port group 260.

In the first and second embodiments described above, each state of themode signal 250 (for example, high level or low level) is correspondingto which mode (the normal mode or the high-impedance mode) of thetri-state buffer component 241 or 330 can be determined according to theactual requirement. However, the level of the mode signal 250 and thecorresponding mode are not limited in the present embodiment.

Third Embodiment

FIG. 4 is a functional block diagram of a non-volatile memory controlleraccording to the third embodiment of the present invention. Referring toFIG. 4, the difference between the present embodiment and the firstembodiment is that in the present embodiment, the mode signal 250 iscoupled to the host interface unit 220. Besides the coupling of the modesignal 250, the other functional blocks in FIG. 3 are similar to thosein FIG. 2 therefore will not be described herein.

The mode signal 250 is sent to the processing unit 122 through the hostinterface unit 220. The processing unit 122 issues a command accordingto the mode signal 250 to the tri-state buffer component 430 of thememory interface unit 420 through a bus. The mode signal 250 controlsthe tri-state buffer component 430 to operate in the high-impedance modeor the normal mode. When the tri-state buffer component 430 operates inthe high-impedance mode, the firmware update fixture 230 can update thefirmware in the non-volatile memory 160 directly on the circuit board.The tri-state buffer component 430 may be implemented by referring tothe tri-state buffer component 241 illustrated in FIG. 2 or thetri-state buffer component 330 illustrated in FIG. 3, or the tri-statebuffer component 430 may also be implemented through other methods.

Fourth Embodiment

FIG. 5 is a functional block diagram of a non-volatile memory controller500 according to the fourth embodiment of the present invention.Referring to FIG. 5, the difference between the present embodiment andthe first embodiment is that in the present embodiment, the tri-statebuffer component of the memory interface unit 510 is implemented byusing a bidirectional buffer 540 in the memory control unit 520. Byserving the bidirectional buffer 540 as the tri-state buffer component,no additional tri-state buffer component is to be disposed between thememory control unit 520 and the non-volatile memory 160 in the memoryinterface unit 510. In the present embodiment, besides the memoryinterface unit 510, the other functional blocks in FIG. 5 are similar tothose in FIG. 2 therefore will not be described herein.

The memory control unit 520 includes a control circuit 530 and at leastone bidirectional buffer 540. The mode signal 250 is sent to the controlcircuit 530. In the normal mode, the mode signal 250 is disabled, andthe control circuit 530 correspondingly sets the bidirectional buffer540 to be in an input buffer mode, an output buffer mode, or thehigh-impedance mode according to the control of the processing unit 122.Accordingly, the processing unit 122 can access the non-volatile memory160 through the control circuit 530. Thus, when the host 140 is about toaccess the non-volatile memory 160, the host 140 can access thenon-volatile memory 160 through the non-volatile memory controller 500.If a firmware stored in the non-volatile memory 160 is to be updated,the mode signal 250 is set to the enabled state so that the controlcircuit 530 is temporarily out of the control of the processing unit122. The control circuit 530 correspondingly sets the bidirectionalbuffer 540 to the high-impedance mode (i.e., the connection port betweenthe bidirectional buffer 540 and the memory port group 260 is in thehigh-impedance state) according to the mode signal 250. Thus, when thebidirectional buffer 540 (i.e., the tri-state buffer component) operatesin the high-impedance mode, the firmware update fixture 230 can updatethe firmware in the non-volatile memory 160 directly on the circuitboard.

Fifth Embodiment

FIG. 6 is a functional block diagram of a non-volatile memory controlleraccording to the fifth embodiment of the present invention. Referring toFIG. 6, in the fifth embodiment, the processing unit 122 of thenon-volatile memory controller 600 is connected between the hostinterface unit 220 and the memory interface unit 620 in series. Besidesthe series connection, the other functional blocks in the presentembodiment are the same as those in the first embodiment therefore willnot be described herein.

When the host 140 is about to access the non-volatile memory 160, themode signal 250 is sent to the tri-state buffer component 622 in thememory interface unit 620 as a high level enabling signal to allow thetri-state buffer component 622 to operate in the normal mode.Accordingly, the host 140 can access the non-volatile memory 160 throughthe non-volatile memory controller 600. It should be noted that to if afirmware stored in the non-volatile memory 160 is to be updated, themode signal 250 is sent to the tri-state buffer component 622 in thememory interface unit 620 as a low level enabling signal to allow thetri-state buffer component 622 to operate in the high-impedance mode. Inthis case, only the firmware update fixture 230 is connected to thenon-volatile memory 160 through the firmware download port group 280.Thus, the firmware update fixture 230 can update the firmware stored inthe non-volatile memory 160 through the firmware download port group 280and the problem of bus contention can be avoided. The implementation ofthe tri-state buffer component 622 can be referred to the first andsecond embodiment described above and will not be described herein.

In the embodiments described above, the non-volatile memory controller300, 400, 500, or 600 and the non-volatile memory 160 can be integratedinto the same IC (or chip) or may also be respectively implemented indifferent ICs (or chips). If the non-volatile memory controller 300,400, 500, or 600 and the non-volatile memory 160 are respectivelyimplemented in different ICs (or chips), they can be fabricated throughany packaging technique. For example, the non-volatile memory controller300, 400, 500, or 600 and the non-volatile memory 160 can be packagedtogether into a MCP. Or, the non-volatile memory controller 300, 400,500, or 600 and the non-volatile memory 160 can be respectively packagedin different IC packages.

The non-volatile memory controller in foregoing first, second, third,fourth, or fifth embodiment has a plurality of port groups, such as thefirmware download port group 280 and the memory port group 260. If thenon-volatile memory controller and the non-volatile memory are packagedtogether in a MCP (for example, in a memory card package), it is notneeded to dispose any corresponding pin on the surface of the MCP sincethe memory port group 260 is packaged within the MCP. Herein a surfaceof the MCP which is soldered on a PCB (not shown) is defined as a “lowerside”. The firmware download port group 280 may be disposed in thecenter of the lower side, at an edge of the lower side, or on an upperside of the MCP according to the actual requirement.

Additionally, if the non-volatile memory controller 200, 300, 400, 500,or 600 and the non-volatile memory 160 are independently packaged, thememory port group 260 can be disposed at the packaged lower side of thenon-volatile memory controller to be soldered on the PCB. The firmwaredownload port group 280 can be disposed in the center of the lower side,at an edge of the lower side, or on an upper side of the non-volatilememory controller according to the actual requirement.

The dispositions of foregoing port groups can be determined by thosehaving ordinary knowledge in the art according to the requirement of thecircuit layout. The dispositions of these port groups in the presentinvention are not limited to foregoing descriptions of the presentembodiment. Below, the disposition of the firmware download port groupin some embodiments of the present invention will be described withreference to accompanying structural diagrams and exploded diagrams ofMCPs.

FIG. 7 is a diagram illustrating the disposition of pins of a MCPaccording to an embodiment of the present invention. Referring to FIG.7, a lower side of the MCP 700 is illustrated. The MCP 700 includes anon-volatile memory controller and a non-volatile memory. The MCP 700may be a memory card. The layout of the port group 740 in the center ofthe lower side of the MCP 700 can be determined by a designer. The portgroup 740 may include a power port group, a ground port group, and ahost access port group. More importantly, in the present invention, thefirmware download port group 720 (the firmware download port group 280in FIG. 2, 3, 4, or 5) can be disposed at an edge of the lower side ofthe MCP 700 to reduce the complexity of the circuit layout and to makewiring to an external fixture easier. The connection between the MCP 700and the fixture will be described below with reference to FIG. 8 andFIG. 9.

FIG. 8 is a perspective view illustrating the connection between the MCP700 and a fixture 230 according to an embodiment of the presentinvention. Referring to both FIG. 7 and FIG. 8, the MCP 700 and aconnector 822 are disposed on the PCB 820 in FIG. 8. The MCP 700 issoldered on the PCB 820, namely, the pins (for example, the firmwaredownload port group 720) on the lower side of the MCP 700 (as shown inFIG. 7) are soldered to the corresponding bounding pads on the PCB 820.The firmware download port group 720 is connected to the connector 822through the layout of the PCB 820. Even though a male adaptor is usedfor representing the connector 822 in FIG. 8, the implementation of theconnector 822 is not limited thereto, and the connection between thefixture 230 and the connector 822 is not limited to the pattern shown inFIG. 8. For example, in another embodiment of the present invention, thefixture 230 may have a plurality of probes for contacting the connector822, and the connector 822 may be a male adaptor (socket) having aplurality of holes; thus, the fixture 230 and the connector 822 can beelectrically connected to each other by inserting the probes into theholes of the connector 822.

The fixture 230 can be connected to the non-volatile memory controller(for example, the non-volatile memory controller illustrated in FIG. 2,3, 4, 5, or 6) inside the MCP 700 through the connector 822 and thefirmware download port group 720. Thus, the firmware can be updatedbased on the descriptions of foregoing embodiments to allow the fixture230 to write a new firmware into the non-volatile memory 160. Theprocess and method for updating the firmware will not be describedherein.

FIG. 9 is an exploded view illustrating the connection between a MCP anda fixture according to another embodiment of the present invention.Referring to FIG. 9, the difference between FIG. 9 and FIG. 8 is thatthe connector 822 is omitted in FIG. 9. A bounding pad 920 isrespectively disposed corresponding to each pin 910 of the firmwaredownload port group 720 on the surface of the PCB 820 and at an edge ofthe lower side of the MCP 700. The bounding pads 920 respectively havean extension towards the opposite direction of the MCP 700 such that theprobes of the fixture 230 can contact the extensions of the boundingpads 920 correspondingly. Since the firmware download port group 720 isdisposed at the edge of the lower side of the MCP 700, the bounding pads920 and the extensions thereof take up only a small portion of thesurface of the PCB720.

FIG. 10 is an exploded view illustrating the connection between a MCPand a fixture according to yet another embodiment of the presentinvention. Referring to FIG. 10, the difference between the MCP 950 inFIG. 10 and the MCP 700 in FIG. 7 is about the disposed position of thefirmware download port group. In FIG. 7, the firmware download portgroup 720 is disposed at the edge of the lower side of the MCP 700,while in FIG. 10, the firmware download port group 960 is disposed on anupper side of the MCP 950. Since the firmware download port group 960 isdisposed on the upper side of the MCP 950, the probes of the fixture 230can directly contact the firmware download port group 960 to carry outthe firmware update operation. Since the firmware download port group960 is disposed on the upper side of the MCP 950, it does not take upany of the layout area of the PCB 970, and the convenience forconnecting the fixture 230 is greatly improved.

FIG. 11 is a flowchart of a firmware update process according to anembodiment of the present invention. First, in step S810, a mode signalis set to switch a memory interface unit to a high-impedance state.Thus, all the signals of the memory interface unit connected to thenon-volatile memory are turned off. Then, in step S820, a fixture forupdating the firmware is connected to the non-volatile memorycontroller. Next, in step S830, whether the non-volatile memory forupdating the firmware exists is determined. If the non-volatile memorydoes not exist (i.e., “no” in step S830), in step S831, the fixtureautomatically shuts off the power supply and stops the operation forupdating the firmware. Contrarily, if the non-volatile memory exists(i.e., “yes” in step S830), in step S840, the firmware update fixturewrites a new firmware into the non-volatile memory. After that, in stepS850, the fixture checks whether the firmware is updated. If thefirmware update process fails (i.e., “no” in step S850), step S840 isrepeated to update the firmware again. Contrarily, if the firmwareupdate process succeeds (i.e., “yes” in step S850), in step S860, thefixture indicates the success, for example, by flashing a light signal.Eventually, in step S870, the fixture is removed to complete thefirmware update process.

As described above, in the present invention, a non-volatile memorycontroller can update a firmware without taking out the non-volatilememory. As a result, firmware update is made more convenient. Moreover,all the input signal paths connected to the non-volatile memory 160 areswitched to an open state so that the other parts of the circuit won'tbe affected when the firmware in the non-volatile memory is updated.Thereby, the problem of bus contention is avoided. Furthermore, variouspin disposition patterns are provided by the present invention such thatthe convenience in firmware update can be further improved and thelayout area taken by the non-volatile memory controller can be reduced.

It will be apparent to those skilled in the art that variousmodifications and variations can be made to the structure of the presentinvention without departing from the scope or spirit of the invention.In view of the foregoing, it is intended that the present inventioncover modifications and variations of this invention provided they fallwithin the scope of the following claims and their equivalents.

1. A non-volatile memory controller, comprising: a firmware downloadport group, for coupled to a firmware update fixture; a memory interfaceunit, comprising at least one tri-state buffer component, wherein thememory interface unit is coupled to a non-volatile memory and thefirmware download port group through the tri-state buffer component, andthe tri-state buffer component determines whether to operate in ahigh-impedance mode or a normal mode according to a mode signal; aprocessing unit, coupled to the memory interface unit, wherein theprocessing unit accesses the non-volatile memory through the memoryinterface unit; and a host interface unit, coupled to the processingunit, wherein the processing unit provides a processing interfacethrough the host interface unit to allow a host to access thenon-volatile memory; wherein when the tri-state buffer componentoperates in the high-impedance mode according to the mode signal, thefirmware update fixture writes a new firmware into the non-volatilememory through the firmware download port group.
 2. The non-volatilememory controller according to claim 1, wherein the memory interfaceunit comprises: the at least one tri-state buffer component; and amemory control unit, coupled between the tri-state buffer component andthe processing unit; wherein the processing unit accesses thenon-volatile memory through the memory control unit.
 3. The non-volatilememory controller according to claim 1, wherein the memory interfaceunit comprises: a memory control unit, coupled between the non-volatilememory and the processing unit, wherein the memory control unitcomprises: at least one bidirectional buffer, serving as the at leastone tri-state buffer component; and a control circuit, coupled betweenthe bidirectional buffer and the processing unit, wherein the controlcircuit sets the bidirectional buffer to be in an input buffer mode, anoutput buffer mode, or the high-impedance mode according to theprocessing unit and the mode signal, and the processing unit accessesthe non-volatile memory through the control circuit.
 4. The non-volatilememory controller according to claim 1, wherein the tri-state buffercomponent is a tri-state buffer.
 5. The non-volatile memory controlleraccording to claim 1, wherein the tri-state buffer component comprises:a buffer; a switch, coupled between the buffer and the non-volatilememory, wherein the switch is in an “off” state in the high-impedancemode, and the switch is in an “on” state in the normal mode.
 6. Thenon-volatile memory controller according to claim 1, being packaged withthe non-volatile memory in a multi-chip package (MCP).
 7. Thenon-volatile memory controller according to claim 6, wherein a lowerside of the MCP is soldered on a printed circuit board (PCB), and thefirmware download port group is disposed on an upper side of the MCP. 8.The non-volatile memory controller according to claim 6, wherein a lowerside of the MCP is soldered on a PCB, and the firmware download portgroup is disposed at an edge of the lower side of the MCP.
 9. Thenon-volatile memory controller according to claim 1, wherein a packagedlower side of the non-volatile memory controller is soldered on a PCB,and the firmware download port group is disposed on a packaged upperside of the non-volatile memory controller.
 10. The non-volatile memorycontroller according to claim 1, wherein a packaged lower side of thenon-volatile memory controller is soldered on a PCB, and the firmwaredownload port group is disposed at an edge of the packaged lower side ofthe non-volatile memory controller.
 11. A memory card, comprising: anon-volatile memory; and a non-volatile memory controller, comprising: afirmware download port group, for coupled to a firmware update fixture;a memory interface unit, comprising at least one tri-state buffercomponent, wherein the memory interface unit is coupled to thenon-volatile memory and the firmware download port group through thetri-state buffer component, and the tri-state buffer componentdetermines whether to operate in a high-impedance mode or a normal modeaccording to a mode signal; a processing unit, coupled to the memoryinterface unit, wherein the processing unit accesses the non-volatilememory through the memory interface unit; and a host interface unit,coupled to the processing unit, wherein the processing unit provides aprocessing interface through the host interface unit to allow a host toaccess the non-volatile memory; wherein when the tri-state buffercomponent operates in the high-impedance mode according to the modesignal, the firmware update fixture writes a new firmware into thenon-volatile memory through the firmware download port group.
 12. Thememory card according to claim 11, wherein the memory interface unitcomprises: the at least one tri-state buffer component; and a memorycontrol unit, coupled between the tri-state buffer component and theprocessing unit; wherein the processing unit accesses the non-volatilememory through the memory control unit.
 13. The memory card according toclaim 11, wherein the memory interface unit comprises: a memory controlunit, coupled between the non-volatile memory and the processing unit,wherein the memory control unit comprises: at least one bidirectionalbuffer, serving as the at least one tri-state buffer component; and acontrol circuit, coupled between the bidirectional buffer and theprocessing unit, wherein the control circuit sets the bidirectionalbuffer to be in an input buffer mode, an output buffer mode, or thehigh-impedance mode according to the processing unit and the modesignal, and the processing unit accesses the non-volatile memory throughthe control circuit.
 14. The memory card according to claim 11, whereinthe tri-state buffer component is a tri-state buffer.
 15. The memorycard according to claim 11, wherein the tri-state buffer componentcomprises: a buffer; a switch, coupled between the buffer and thenon-volatile memory, wherein the switch is in an “off” state in thehigh-impedance mode, and the switch is in an “on” state in the normalmode.
 16. The memory card according to claim 11, wherein thenon-volatile memory controller and the non-volatile memory are bothpackaged in a MCP.
 17. The memory card according to claim 16, wherein alower side of the MCP is soldered on a PCB, and the firmware downloadport group is disposed on an upper side of the MCP.
 18. The memory cardaccording to claim 16, wherein a lower side of the MCP is soldered on aPCB, and the firmware download port group is disposed at an edge of thelower side of the MCP.
 19. The memory card according to claim 11,wherein a packaged lower side of the non-volatile memory controller issoldered on a PCB, and the firmware download port group is disposed on apackaged upper side of the non-volatile memory controller.
 20. Thememory card according to claim 11, wherein a packaged lower side of thenon-volatile memory controller is soldered on a PCB, and the firmwaredownload port group is disposed at an edge of the packaged lower side ofthe non-volatile memory controller.